If you have custom SQL views, be sure to refresh the metadata for them, to avoid database errors when upgrading iMIS. Views are created with schema information (column data types and sizes) as it is at that moment; if a column is later changed, renamed, or dropped, the view's cached value is out of sync. Using such a view can cause errors and unexpected issues, such as strings being truncated. User-created views easily become out of date because the iMIS schema changes from version to version.
1. Follow the iMIS Community post: Refreshing View Meta-Data.
2. Check the report for errors. Keep in mind:
□ SQL Server only reports the first bad column it encounters in a given view, even if there are several. Therefore, run the script repeatedly until no errors remain.
□ If you've renamed the column in the view, the column name listed in this output is the original column name in the Table, not the name used in the View.
3. If any errors are reported, fix the problem views immediately. This may involve
□ renaming a column in your view definition
□ dropping a column altogether
□ getting the data from a new or different table
□ dropping an obsolete view
□ republishing the associated Business Object in BOD, if the view name starts with vBo (an automatically generated view)
4. Once the view is fixed, run the script again.
5. When errors no longer occur, proceed with the upgrade.